| Author |
Thread Statistics | Show CCP posts - 32 post(s) |
Dealth Striker
Striker Ltd
31
   |
Posted - 2014.05.29 14:20:00 -
[1] - Quote
Strange... Just received my station job delivery but not my POS one.
Station job is oldest and POS newest
Maybe it is stations then POSes?
Striker Out!! |
Dealth Striker
Striker Ltd
31
|
Posted - 2014.05.30 02:33:00 -
[2] - Quote
CCP Explorer wrote:Querns wrote:Dinsdale Pirannha wrote:I look forward to all the other mechanics you will wreck by ramming through massive changes without proper testing.
If you guys seriously believe that changes of this magnitude and complexity, larger than Apochrypha, are going to be all sorted with at most 6 weeks of testing on Sisi, you are seriously deluded.
CCP, use whatever common sense you have left, stop listening to your null sec cartel "advisors", and postpone this disaster-in-waiting until the fall, and allow for proper testing on Sisi. What proof do you have that the issue was even related to the pending industry changes? I don't think he has any, but this was industry-related pre-cleanup. Testing of the industry changes begins on Singularity around 10 June and the release is currently scheduled for 22 July.
I submitted 2 manufacturing jobs prior to downtime.
I logged off for the night and when I logged in while this crap was happening, I did not take an update of any kind.
I received the fore mentioned delivery error on both completed jobs.
So the error was on the server side, and since the players supposedly do not have access to change anything on the server side, it had to come from CCP.
Since this was an industry error, it would point to something to do with the upcoming industry changes.
I am sure we will never get a straight answer as it took quite a few players to finally get CCP to look at it.
Just a prelim to what is coming
Striker Out!! |
Dealth Striker
Striker Ltd
31
|
Posted - 2014.05.30 07:05:00 -
[3] - Quote
Loraine Gess wrote:Dealth Striker wrote:CCP Explorer wrote:Querns wrote:Dinsdale Pirannha wrote:I look forward to all the other mechanics you will wreck by ramming through massive changes without proper testing.
If you guys seriously believe that changes of this magnitude and complexity, larger than Apochrypha, are going to be all sorted with at most 6 weeks of testing on Sisi, you are seriously deluded.
CCP, use whatever common sense you have left, stop listening to your null sec cartel "advisors", and postpone this disaster-in-waiting until the fall, and allow for proper testing on Sisi. What proof do you have that the issue was even related to the pending industry changes? I don't think he has any, but this was industry-related pre-cleanup. Testing of the industry changes begins on Singularity around 10 June and the release is currently scheduled for 22 July. I submitted 2 manufacturing jobs prior to downtime. I logged off for the night and when I logged in while this crap was happening, I did not take an update of any kind. I received the fore mentioned delivery error on both completed jobs. So the error was on the server side, and since the players supposedly do not have access to change anything on the server side, it had to come from CCP. Since this was an industry error, it would point to something to do with the upcoming industry changes. I am sure we will never get a straight answer as it took quite a few players to finally get CCP to look at it. Just a prelim to what is coming CCP staff respond quickly very early in the morning, and you think it's slow and a conspiracy? How stupid must you be to believe that?
You like making things up since you have a tendency to spin people's comments to your line of thought.
I never said they were slow.
Maybe spend more time understanding what people are writing instead of rushing though the comments so that you can quickly write a fanboi comment. That way you will not look like a fool.
If CCP knew what the problem was and they fixed it. Why did Explorer dodge the question about what happened? I think it is so they can polish a response. But this is CCP - there is no such thing of them doing stuff like this in the past -- lol
Striker Out!! |
Dealth Striker
Striker Ltd
31
|
Posted - 2014.05.30 08:56:00 -
[4] - Quote
CCP Explorer wrote:Dealth Striker wrote:If CCP knew what the problem was and they fixed it. Why did Explorer dodge the question about what happened? I think it is so they can polish a response. See my reply above, so I can talk to the team.
As a director, I would hope that you knew what the problem was when you first posted about we are aware of the problem and are fixing it.
Striker Out!! |
Dealth Striker
Striker Ltd
31
|
Posted - 2014.06.03 01:57:00 -
[5] - Quote
Probably will not get anything now.
The next classic customer service excuse will be "We are too busy working on the release"
They must know what the problem was and what caused it.
Not only do they have to know in order to fix it, the higher-ups will want to know what happened to tick off their customer base.
The customer service people would definitely want to know so to field the tickets caused.
But, this is small potatoes compared to the buffet happening shortly.
Hope everyone has taken their screenshots of their valuable assets, etc -- it could be a bumpy ride after the release.
I have gotten to the point of taking out my probes and missiles in their launchers before downtimes as they tend to just vanish every once in awhile.
Striker Out!! |
Dealth Striker
Striker Ltd
31
|
Posted - 2014.06.03 14:49:00 -
[6] - Quote
CCP Explorer wrote:So, the details:
When blueprints are used for science & industry jobs, we move them into a special location so that they are not accessible while being used. After the job completes then we return the blueprint (if it's an original or a copy with remaining runs) or put into a junkyard (copy with no remaining runs).
There is an old bug in the system that causes blueprints to remain in that special location when they should have been moved into a junkyard. There are about 41 million blueprints there now. The aim of this cleanup was to find all those blueprints and move them. The script had an error causing some additional blueprint copies that were a part of a current job to be moved as well.
Through a series of unfortunate miscommunication the cleanup was run by system administrators in Shanghai when the dev team in Reykjav+¡k was on a public holiday, which explains the delayed response. Once the issue was discovered we reverted the entire cleanup.
Thank you and I apologize
Striker Out!! |
| |
|